Location derived presence information

ABSTRACT

The number of messages required in networks where both location and presence services are deployed may be reduced, by retrieving presence data from messages otherwise intended to provide only location information. Thus, information determined in a location service scheme is utilized to provide a presence service as well. A location server requests mobile subscriber (MS) information from a Core Network (CN) Node (i.e. HLR, MSC, etc.) that can be used in determining the Location of the MS. A single message aggregates retrieval of information for two services, specifically, for both location and presence.

This application is a continuation of U.S. patent application Ser. No. 14/021,319, entitled “Location Derived Presence Information”, to Hines et al., filed on Sep. 9, 2013; which in turn is a continuation of U.S. patent application Ser. No. 13/200,821, entitled “Location Derived Presence Information,” to Hines et al., filed on Oct. 3, 2011, now U.S. Pat. No. 8,532,277; which in turn is continuation of U.S. patent application Ser. No. 12/007,947, entitled “Location Derived Presence Information,” to Hines et al., filed on Jan. 17, 2008, now U.S. Pat. No. 8,032,112; which in turn is a continuation of U.S. patent application Ser. No. 10/395,217, entitled “Location Derived Presence Information,” to Hines et al., filed on Mar. 25, 2003, now U.S. Pat. No. 7,426,380; which claims priority from U.S. Provisional Appl. No. 60/367,708, entitled “Location Derived Presence Information”, filed Mar. 28, 2002, by Hines et al., the entirety of all of which are explicitly incorporated herein by reference.

BACKGROUND OF THE INVENTION

1. Field of the Invention

This invention relates generally to wireless communication carriers. More particularly, it relates to location and presence-based services for the wireless industry.

2. Background of Related Art

The term “presence” in the wireless world typically relates to a network answer to the simple question “Are you available?”. For instance, if a subscriber's wireless device is turned off, they would not be available. However, if a subscriber's wireless device is turned on, and in communication with a carrier, the carrier would most likely be able to indicate to a relevant request that the subscriber is available and thus “present”. The functions and use of presence information is well known in the art.

Location information regarding subscribers is increasingly becoming available in a wireless network. This is particularly true in systems that comply with E-9-1-1 requirements. Location information relates to absolute coordinates of a wireless device.

Both Location and Presence services are message intensive on telecom networks. Message reduction in general is desirable, both to allow increased capacity in a wireless network, as well as to improve reliability of the system by reducing the number of messages.

SUMMARY OF THE INVENTION

In accordance with the principles of the present invention, a method and apparatus provides presence information regarding a wireless device. A request for location information regarding a wireless device is received. Presence information regarding the wireless device is provided in response to the receipt of the request for location information regarding the wireless device.

BRIEF DESCRIPTION OF THE DRAWINGS

Features and advantages of the present invention will become apparent to those skilled in the art from the following description with reference to the drawings, in which:

FIG. 1 shows generally a location request.

FIG. 2 shows a LoCation Services (LCS) request generating a presence response, in accordance with the principles of the present invention.

DETAILED DESCRIPTION OF ILLUSTRATIVE EMBODIMENTS

The present invention recognizes the duplicity of information provided by location and presence services, and reduces the number of messages required in networks where both Location and Presence services are deployed.

To reduce the amount of messaging within the core network, the present invention retrieves presence data from messages intended to provide location information. Thus, information determined in a Location service scheme is utilized to provide a presence service as well.

In accordance with the present invention, a Location Server requests mobile subscriber (MS) information from a Core Network (CN) Node (i.e. HLR, MSC, etc.) that can be used in determining the Location of the MS. In most cases the messages used for requesting Location and Presence services are the same. The proposed concept uses a single message to aggregate information for two services, specifically Location and Presence.

Entirely new revenue streams may be realized by carriers through a location services solution, e.g., the Xypoint Location Platform (XLP) available from TeleCommunication Systems, Inc. in Annapolis, Md. The XLP preferably integrates three centers that wireless carriers should have to effectively gather, manage, protect and distribute wireless data, and ultimately, collect revenue from subscribers for doing so. With the ability to offer the full array of location-based services-everything from enhanced 411 services, to location-based games, child tracking and location-specific advertising-carriers can add a whole new profit center to their business models, including generating non-subscriber revenue. The three module centers in the exemplary XLP used in the disclosed embodiments are a Location Center, a Presence Center, and a Privacy Center.

Location Center—Determines the location of mobile users from the wireless network and provides a single point of access for location-based applications. The XLP Location Center preferably includes a mobile positioning center (MPC), e.g., a fully J-STD-036-compliant Mobile Positioning Center (MPC) to deliver E911 Phase I services.

Presence Center—Enhances an application's ability to communicate with the mobile user by determining the state and availability of the mobile user to receive a text message, WAP push or incoming call. Presence enables applications such as instant messaging and allows for options such as determining who on your “buddy list,” is available.

Privacy Center—Ensures that carriers and mobile subscribers are firmly in control of their data. It allows users to choose exactly which location and presence information to make available to specific vendors or other users.

The XLP is preferably implemented as either a fully turnkey (in-house), hosted or hybrid solution, allowing carriers to pick and choose the best solution to meet their business needs. Whether a carrier opts for in-house or hosted services, the XLP provides a highly available and scalable distributed network architecture. The XLP also offers carriers the flexibility to choose the position determining entity (PDE) that will best meet their current needs while also minimizing over-lapping integration of applications and services.

The MPC technology integrated within the XLP's Location Center has been deployed to support E911 Phase I services. The Xypoint Location Platform available from TeleCommunication Systems, Inc. has been integrated with well over 100 commercially available switches-including Lucent, Nortel, Motorola and Ericsson. The XLP is preferably network independent and supports all major wireless interfaces, including GSM, CDMA, TDMA and AMPS.

FIG. 1 shows generally a location request to a core network node containing pertinent location information, resulting not only in a return of location information, but also in the spawning of presence information.

In particular, as shown in FIG. 1, a location server 202 requests location information regarding a particular mobile subscriber (MS) from a core network node 204, e.g., from a Mobile Switch Center (MSC). Requested information regarding a particular wireless device (MS) may include, e.g., attach, detach, and location area update. The location server 202 may also request information regarding the wireless device such as attach, detach and/or location area update from a Packet Date Node (e.g., SGSN, GGSN, or PDSN).

Typically, location information regarding a particular wireless device is requested of a home location register (HLR). In accordance with the principles of the present invention, the home location register can also serve as a basis for presence services. Exemplary presence services may include, e.g., the state and/or status of a subscriber.

Importantly, in accordance with the present invention, information relating to presence is spawned or triggered by a location request. The presence information may or may not be returned along with the location information, but preferably is included within the message (or messages) containing location information.

FIG. 2 shows an exemplary LoCation Services (LCS) request generating a response including presence information in more detail, in accordance with the principles of the present invention.

In particular, FIG. 2 shows exemplary messaging between a presence client 102, a location service client 104, a location/presence server 106, a home location register (HLR) 108, a core network node such as an MSC or packet data node 110, and a radio access network (RAN) 112.

In the exemplary embodiment, the messaging cycle is initiated (shown in Step 1) by a location services client 104, that transmits a location request message to a location services/presence server 106 in the relevant carrier's network.

In step 2, a Provide Subscriber Info message is transmitted by the location services/presence services server 106 to the home location register 108 (or other node containing location and/or presence information). The Provide Subscriber Info message can request location information and/or subscriber state. In this use case, location information regarding a particular subscriber is being requested, and within the same message, presence information such as subscriber state may also be requested. Requested presence information can include, e.g., idle, bust, not reachable, etc.

In step 3, the network node containing the location and presence information (e.g., the Home Location Register (HLR) 108) provides the requested location information and presence information (e.g., idle, bust, not reachable, etc.) back to the location services/presence services server 106.

In step 4, the location services/presence services server 106 uses the returned subscriber info, and transmits a Presence Service Response to a relevant presence application, e.g., a presence client 102 depicted in FIG. 2.

This ‘freebie’ presence information is an important aspect of the present invention. For instance, an entirely separate presence application 102 may register with a particular carrier, perhaps paying suitable fees, for the right to receive presence information for those wireless devices that have had location information returned. This avoids the need for the presence client 102 to separately request presence information regarding that particular wireless device.

In step 5, the location services/presence services server 106 requests updated location information of the wireless network, i.e., sending a request for current location information from a relevant network node (e.g., the MSC or packet data node 110).

The MSC, packet data node 110, etc. may determine a current location of the relevant wireless device using any suitable location technology, e.g., using a global positioning satellite (GPS) system, using triangulation, using angle of arrival, etc.

As part of the determination of a current location of the wireless device, as shown in step 6, the location request may be forwarded to a Radio Access Network. This would be necessary for certain locating technologies (e.g., for triangulation, angle of arrival, etc.). If a global positioning satellite system is utilized, the location request may be forwarded to a suitable GPS application in the wireless network that receives GPS location information regarding a relevant wireless device.

In step 7, a response to the update location information request is transmitted to the location services/presence services server 106. (The updated location information may also be forwarded to the HLR (not shown in FIG. 2) to update the current location of the relevant wireless device).

Lastly, in step 8, the location information initially requested by the LCS application or client 104 is returned. This returned information ideally includes current location information freshly obtained from the MSC 110 or other network node, but may instead be cached location information stored in the HLR 108 if the location information is not returned within a sufficient time window (e.g., causing a timeout).

The present invention provides benefits such as reducing core network messaging traffic, providing better XLP performance, and allowing the use of cached presence data relating to wireless devices, allowing quick and easy access to presence data.

While the invention has been described with reference to the exemplary embodiments thereof, those skilled in the art will be able to make various modifications to the described embodiments of the invention without departing from the true spirit and scope of the invention. 

What is claimed is:
 1. A method of providing service to a presence client device, comprising: receiving, at a physical network server, a request for location regarding a given wireless device from a location requesting device; and transmitting a presence service response, to the presence client device registered to receive presence information for the given wireless device, in response to said request for location from said location requesting device, wherein the presence service response includes data characterizing an availability of the given wireless device to communicate with another node; wherein said presence service response is triggered by said request for location, and said location requesting device is a different device from said presence client device.
 2. The method of providing service to a presence client device according to claim 1, wherein: said presence service response is included within a message containing a location response.
 3. The method of providing service to a presence client device according to claim 1, wherein: said presence service response indicates an availability of the given mobile device to receive a text message.
 4. The method of providing service to a presence client device according to claim 1, wherein: said presence service response indicates an availability of the given mobile device to receive a wireless application protocol (WAP) push.
 5. The method of providing service to a presence client device according to claim 1, wherein: said presence service response indicates an availability of the given mobile device to receive an incoming call.
 6. The method of providing service to a presence client device according to claim 1, wherein: said presence service response indicates a state and status of the given mobile device.
 7. The method of providing service to a presence client device according to claim 1, wherein said network server comprises: a home location register.
 8. The method of providing service to a presence client device according to claim 1, wherein said network server comprises: an indication of an idle state of the given mobile device.
 9. The method of providing service to a presence client device according to claim 1, wherein said network server comprises: an indication of a bust state of the given mobile device.
 10. The method of providing service to a presence client device according to claim 1, wherein said presence service response comprises: an indication that the given mobile device is unavailable. 